|
|
Hi Jason, RCU should not be unpaired after idle timeout, usually STB disconnects with RCU. Idle timeout is used to recover BLE connection and save power if peer doesn't response within a period. More, even idle timeout is disabled on STB side, RCU still has its own idle timeout mechanism. Hence, connection will also be disconnected. Thanks ! |
|
|
HI Jason. skb manager ask whether if it is related to CTS fail if disable for idle timeout. Thanks. |
|
|
HI Kerwin per talk to you, intek try to do for disable idle time out as below. the function in an attached image is located in stack/I2cap/i2c_utils.cc as below , it is modified. if (start_timeout) If (start_timeout && timeout_ms != (0xffff * 1000)) idleTimeout.JPG (48,897 bytes) |
|
|
HI Kerwin if you apply it, please give a target date. Thanks. |
|
|
Hi Jason, In order to have same behavior on Smart3, please give more detailed about the modification. Thanks ! |
|
|
hi kerwin we receive some information from Intek. they apply it on AI2 Box. so we don't have a modified point on Smart3. Thanks. |
|
|
Hi Jason, Per talked, Intek's patch works on Android P. However, Google has released a patch to check L2CAP timeout for fixed BLE channel on Android Q. (https://android.googlesource.com/platform/system/bt/+/fadc6b9b0280d7db277f666fd0f9d2602a7e08f4%5E%21/#F1) We are going to migrate to Android Q for Smart3 box. As a result, we don't need to apply Intek's patch on Android Q. Thanks ! |
|
|
hi kerwin this issue is closed |
- yk.jung ( (ALTech) Younkwang Jung ) developer
